This document describes the head-end architecture and synchronization for digital video broadcasting using SimulCrypt. It outlines the system components including an event information scheduler, SimulCrypt synchronizer, entitlement control message generator, entitlement management message generator, and multiplexer. It also describes the interfaces between these components, covering processes like channel and stream establishment and closure, as well as bandwidth allocation and status reporting.
The document provides implementation guidelines for using the DVB Simulcrypt standard, including describing the architecture and protocols, clarifying differences between protocol versions, explaining state diagrams and processes, and providing recommendations for error handling, redundancy management, and custom signaling. It aims to facilitate reliable implementation of the Simulcrypt model and interfaces between broadcasters, network operators, and manufacturers.
This document provides specifications for service information (SI) in digital video broadcasting (DVB) systems, including:
- It defines SI as data tables for identifying services, events, and other information in DVB signal streams.
- SI tables are divided into network information tables, service description tables, event information tables, and other tables for time/date, running status, etc.
- Descriptors are also defined to provide additional information about services, components, parental ratings, etc. within the tables.
This document is a technical specification from ETSI (European Telecommunications Standards Institute) that defines the mobile radio interface layer 3 specification for GSM (Global System for Mobile communications), specifically version 7.8.0 from 1998. It contains specifications for radio resource management procedures in both circuit-switched and packet-switched modes, including procedures for idle mode, dedicated mode, group receive/transmit modes, and changing between dedicated channels. It also references related documents and defines terms and abbreviations used.
This document provides an overview of Codan's 6700/6900 series block up converter (BUC) systems and components. It describes the BUC, low-noise block converter (LNB), and redundancy systems. It also covers installation, operation, and troubleshooting of the systems. The document contains information on frequency bands, conversion plans, interfaces, cable connections, monitor/control, commands, maintenance procedures, and compliance standards.
This document provides an overview of service information (SI) in digital video broadcasting (DVB) systems, including sections like the network information section (NIT), service description section (SDT), bouquet association section (BAT), program association section (PAT), conditional access section (CAT), transport stream description section (TSDT), event information section (EIT), and running status section (RST). It includes syntax diagrams and details for each section, such as table IDs, section lengths, descriptors, and other fields. It also provides the PID and refresh interval requirements for each table type.
The RSA cryptosystem document discusses:
1) The RSA cryptosystem uses a public and private key to encrypt and decrypt messages based on large prime number factorization.
2) An example is provided where a message is encrypted with a public key and decrypted with a private key.
3) The security of RSA relies on the difficulty of factoring large numbers, as factorization algorithms take exponential time relative to the number of bits.
This document discusses the basics of BISS scrambling. It describes BISS mode 1, which uses a session word, and BISS mode E, which encrypts the session word using an identifier and encryption algorithm. BISS mode E provides an additional layer of protection for transmitting the session word. The document also covers calculating the encrypted session word, using buried and injected identifiers, and how to operate scramblers in the different BISS modes.
This document discusses image compression using the discrete cosine transform (DCT). It develops simple Mathematica functions to compute the 1D and 2D DCT. The 1D DCT transforms a list of real numbers into elementary frequency components. It is computed via matrix multiplication or using the discrete Fourier transform with twiddle factors. The 2D DCT applies the 1D DCT to rows and then columns of an image, making it separable. These functions illustrate how Mathematica can be used to prototype image processing algorithms.
The document provides implementation guidelines for using the DVB Simulcrypt standard, including describing the architecture and protocols, clarifying differences between protocol versions, explaining state diagrams and processes, and providing recommendations for error handling, redundancy management, and custom signaling. It aims to facilitate reliable implementation of the Simulcrypt model and interfaces between broadcasters, network operators, and manufacturers.
This document provides specifications for service information (SI) in digital video broadcasting (DVB) systems, including:
- It defines SI as data tables for identifying services, events, and other information in DVB signal streams.
- SI tables are divided into network information tables, service description tables, event information tables, and other tables for time/date, running status, etc.
- Descriptors are also defined to provide additional information about services, components, parental ratings, etc. within the tables.
This document is a technical specification from ETSI (European Telecommunications Standards Institute) that defines the mobile radio interface layer 3 specification for GSM (Global System for Mobile communications), specifically version 7.8.0 from 1998. It contains specifications for radio resource management procedures in both circuit-switched and packet-switched modes, including procedures for idle mode, dedicated mode, group receive/transmit modes, and changing between dedicated channels. It also references related documents and defines terms and abbreviations used.
This document provides an overview of Codan's 6700/6900 series block up converter (BUC) systems and components. It describes the BUC, low-noise block converter (LNB), and redundancy systems. It also covers installation, operation, and troubleshooting of the systems. The document contains information on frequency bands, conversion plans, interfaces, cable connections, monitor/control, commands, maintenance procedures, and compliance standards.
This document provides an overview of service information (SI) in digital video broadcasting (DVB) systems, including sections like the network information section (NIT), service description section (SDT), bouquet association section (BAT), program association section (PAT), conditional access section (CAT), transport stream description section (TSDT), event information section (EIT), and running status section (RST). It includes syntax diagrams and details for each section, such as table IDs, section lengths, descriptors, and other fields. It also provides the PID and refresh interval requirements for each table type.
The RSA cryptosystem document discusses:
1) The RSA cryptosystem uses a public and private key to encrypt and decrypt messages based on large prime number factorization.
2) An example is provided where a message is encrypted with a public key and decrypted with a private key.
3) The security of RSA relies on the difficulty of factoring large numbers, as factorization algorithms take exponential time relative to the number of bits.
This document discusses the basics of BISS scrambling. It describes BISS mode 1, which uses a session word, and BISS mode E, which encrypts the session word using an identifier and encryption algorithm. BISS mode E provides an additional layer of protection for transmitting the session word. The document also covers calculating the encrypted session word, using buried and injected identifiers, and how to operate scramblers in the different BISS modes.
This document discusses image compression using the discrete cosine transform (DCT). It develops simple Mathematica functions to compute the 1D and 2D DCT. The 1D DCT transforms a list of real numbers into elementary frequency components. It is computed via matrix multiplication or using the discrete Fourier transform with twiddle factors. The 2D DCT applies the 1D DCT to rows and then columns of an image, making it separable. These functions illustrate how Mathematica can be used to prototype image processing algorithms.
Dani Pedrosa won the MotoGP race at Laguna Seca, finishing just 0.344 seconds ahead of Valentino Rossi in second and 1.926 seconds ahead of Jorge Lorenzo in third. Casey Stoner finished fourth, over 12 seconds behind Pedrosa. There were several crashes during the race, with Andrea Dovizioso, Sete Gibernau, and Gabor Talmacsi all falling out of contention. James Toseland received a ride through penalty for a jump start.
1) Reed-Solomon codes are a type of error-correcting code invented in 1960 that can detect and correct multiple symbol errors. They work by encoding data into redundant symbols that can be used to detect and locate errors.
2) Reed-Solomon codes are particularly good at correcting burst errors, where a block of symbols are corrupted together by noise. Even if an entire block of bits is corrupted, the code can still correct the errors by replacing the corrupted symbol.
3) The error correction capability of Reed-Solomon codes increases with larger block sizes, as noise is averaged over more symbols. However, implementing Reed-Solomon codes also becomes more complex with higher redundancy.
1) The document describes a modification to the Huffman coding used in JPEG image compression. It proposes pairing each non-zero DCT coefficient with the run-length of subsequent (rather than preceding) zero coefficients.
2) This allows using separate optimized Huffman code tables for each DCT coefficient position, improving compression by 10-15% over standard JPEG coding.
3) The decoding procedure is not changed and no end-of-block marker is needed, providing advantages with no increase in complexity.
The document provides implementation guidelines for using the DVB Simulcrypt standard, including describing the architecture and protocols, clarifying differences between protocol versions, explaining state diagrams and behaviors, and providing recommendations for error handling, redundancy management, and custom signaling profiles to facilitate reliable and efficient Simulcrypt headend implementation.
This document provides implementation guidelines for the DVB Simulcrypt standard. It describes the architecture and protocols involved in simulcrypt systems, including the ECMG protocol between the security client system and conditional access modules, and the EMMG/PDG protocol between conditional access modules and multiplex equipment. The document outlines differences between version 1 and 2 of the standards, and provides recommendations for compliance. It also includes detailed state diagrams and descriptions of the protocols involved.
This document discusses digital set-top boxes (STBs) and related standards. It covers:
1) The DVB standards for digital TV broadcasting via different transmission media, including DVB-T for terrestrial, DVB-S for satellite, and DVB-C for cable. These share source coding/compression and service multiplexing standards.
2) STBs will be needed until integrated digital TVs are cheaper. Affordable STBs are key for digital TV adoption. Common standards help lower STB costs through economies of scale.
3) "Open architecture" and "interoperability" mean the STB functionality is defined by public standards and can receive services across networks, respectively. The
1) The document discusses quantization and pulse code modulation (PCM) in voice signal encoding. PCM assigns 256 possible values to digitally represent analog voice samples, divided into chords and steps on a linear scale.
2) A logarithmic quantization scale is better than a linear one for voice signals, as it allocates more quantization steps to lower amplitudes prevalent in speech. This "compressed encoding" improves fidelity.
3) Quantization error occurs when samples with different amplitudes are assigned the same digital value, distorting the reconstructed waveform. Compression helps maintain a higher signal-to-noise ratio especially for low amplitudes.
DVB-S2 is the second-generation specification for satellite broadcasting developed by DVB in 2003. It uses more advanced channel coding (LDPC codes) and modulation formats (QPSK, 8PSK, 16APSK, 32APSK) for a 30% increase in transmission capacity over DVB-S. DVB-S2 allows for adaptive coding and modulation to optimize transmission for each user. It is designed for broadcast, interactive, and professional applications with flexibility to handle different transponder characteristics and content formats.
The STi7167 is an integrated system-on-chip that combines a configurable DVB-T or DVB-C demodulator with STB decoding and display functions. It provides advanced HD and SD video decoding, audio decoding, graphics processing, and connectivity options. The chip's integrated features allow for low cost and small size STB designs for cable or terrestrial networks.
The document discusses DCT/IDCT concepts and applications. It provides an introduction to DCT and IDCT, explaining that they are used widely in video and audio compression. It describes the DCT and IDCT functions and how they work to transform signals between spatial and frequency domains. Examples of one-dimensional and two-dimensional DCT/IDCT equations are also given. Finally, common applications of DCT/IDCT compression techniques are listed, such as in DVD players, cable TV, graphics cards, and medical imaging systems.
The document provides an overview of MPEG-4, a standard that offers both advanced audio and video codecs as well as tools for combining multimedia such as audio, video, graphics and interactivity. It was developed through an open international process to select the best technologies. MPEG-4 codecs like AVC and AAC provide high compression efficiency, having been adopted for HDTV, mobile video, and digital music. Its rich media tools allow interactive experiences combining different media types.
DVB-S2 is the second-generation specification for satellite broadcasting developed by DVB in 2003. It uses more advanced channel coding (LDPC codes) and modulation formats (QPSK, 8PSK, 16APSK, 32APSK) for improved transmission performance, achieving up to a 30% increase in capacity over DVB-S. DVB-S2 allows for backwards compatibility with DVB-S receivers and uses adaptive coding and modulation to optimize transmission for different users and conditions. It provides high flexibility to work with different input streams, modulation schemes, and satellite transponder characteristics.
This document discusses service information (SI) in DVB systems, specifically the discontinuity information section. It provides packet syntax diagrams for an MPEG-2 transport stream, the network information section, service description section, and bouquet association section, which are used to deliver metadata about available TV and radio channels and services. It also includes the syntax for a discontinuity information section, which is used to signal discontinuities in MPEG program streams that are caused by operations like splicing.
This document provides an overview of satellite communications fundamentals. It discusses how satellites provide capabilities not available through landlines, such as mobility and quick implementation. However, satellites are not always the most cost effective solution due to limited frequency spectrum and spatial capacity. The document describes different types of satellite services and configurations, including geostationary and non-geostationary satellites. It also covers topics like frequency reuse, earth station antennas, and satellite link delays.
ATI Courses Satellite Communications Systems Engineering Professional Develop...Jim Jenkins
ATI Courses Satellite Communications Systems Engineering course sampler. This three-day course is designed for satellite communications engineers, spacecraft engineers, and managers who want to obtain an understanding of the "big picture" of satellite communications. Each topic is illustrated by detailed worked numerical examples, using published data for actual satellite communications systems. The course is technically oriented and includes mathematical derivations of the fundamental equations. It will enable the participants to perform their own satellite link budget calculations. The course will especially appeal to those whose objective is to develop quantitative computational skills in addition to obtaining a qualitative familiarity with the basic concepts.
The document provides implementation guidelines for using the DVB Simulcrypt standard, including describing the architecture and protocols, clarifying differences between protocol versions, explaining state diagrams and error handling, and providing recommendations for redundancy management between system components. It aims to facilitate reliable implementation of the DVB Simulcrypt model and interoperable interfaces between conditional access systems.
This document provides implementation guidelines for the DVB Simulcrypt standard. It describes the architecture and protocols involved in simulcrypt systems, including the ECMG protocol between the security client system and conditional access modules, and the EMMG/PDG protocol between conditional access modules and multiplex equipment. The document outlines differences between version 1 and 2 of the standards, and provides recommendations for compliance. It also includes detailed state diagrams and descriptions of the protocols to clarify permissible messages in each state.
This document provides implementation guidelines for the DVB Simulcrypt standard. It describes the architecture and protocols involved in simulcrypt systems, including the ECMG protocol between the security client system and conditional access modules, and the EMMG/PDG protocol between conditional access modules and multiplex equipment. The document outlines differences between version 1 and 2 of the standards, and provides recommendations for compliance. It also includes detailed state diagrams and descriptions of the protocols to clarify permissible messages in each state.
This document provides specifications for Service Information (SI) in Digital Video Broadcasting (DVB) systems. It defines the SI table mechanisms and tables used to describe services, events and other data in DVB transport streams. Section 5 describes the SI table system, including the mapping of sections into transport stream packets and coding of table identifiers. Section 6 defines various descriptors used within the SI tables to provide metadata about services, components, events and other data elements in DVB systems.
This document provides specifications for Service Information (SI) in Digital Video Broadcasting (DVB) systems. It defines the SI table mechanisms and tables used to describe services, events and other data in DVB transport streams. Section 5 describes the SI table system, including the mapping of sections into transport stream packets and coding of table identifiers. Section 6 defines various descriptors used within the SI tables to provide metadata about services, components, events and other data elements in DVB systems.
This document provides a specification for Service Information (SI) in Digital Video Broadcasting (DVB) systems. It defines the SI data tables and descriptors that are used to describe DVB services, events, and other data elements. The SI tables include the Network Information Table (NIT), Bouquet Association Table (BAT), Service Description Table (SDT), Event Information Table (EIT), Time and Date Table (TDT), Time Offset Table (TOT), Running Status Table (RST), Stuffing Table (ST), and Discontinuity Information Table (DIT). The document also specifies over 50 descriptors that provide additional metadata about services, components, events, content, ratings, and other attributes.
This document provides a specification for Service Information (SI) in Digital Video Broadcasting (DVB) systems. It defines the SI data tables and descriptors that are used to describe content, events, and services in DVB systems. The document specifies the SI table mechanism, table definitions, descriptor identification and coding. It also defines Storage Media Interoperability measures for SI implementation on removable storage media.
Dani Pedrosa won the MotoGP race at Laguna Seca, finishing just 0.344 seconds ahead of Valentino Rossi in second and 1.926 seconds ahead of Jorge Lorenzo in third. Casey Stoner finished fourth, over 12 seconds behind Pedrosa. There were several crashes during the race, with Andrea Dovizioso, Sete Gibernau, and Gabor Talmacsi all falling out of contention. James Toseland received a ride through penalty for a jump start.
1) Reed-Solomon codes are a type of error-correcting code invented in 1960 that can detect and correct multiple symbol errors. They work by encoding data into redundant symbols that can be used to detect and locate errors.
2) Reed-Solomon codes are particularly good at correcting burst errors, where a block of symbols are corrupted together by noise. Even if an entire block of bits is corrupted, the code can still correct the errors by replacing the corrupted symbol.
3) The error correction capability of Reed-Solomon codes increases with larger block sizes, as noise is averaged over more symbols. However, implementing Reed-Solomon codes also becomes more complex with higher redundancy.
1) The document describes a modification to the Huffman coding used in JPEG image compression. It proposes pairing each non-zero DCT coefficient with the run-length of subsequent (rather than preceding) zero coefficients.
2) This allows using separate optimized Huffman code tables for each DCT coefficient position, improving compression by 10-15% over standard JPEG coding.
3) The decoding procedure is not changed and no end-of-block marker is needed, providing advantages with no increase in complexity.
The document provides implementation guidelines for using the DVB Simulcrypt standard, including describing the architecture and protocols, clarifying differences between protocol versions, explaining state diagrams and behaviors, and providing recommendations for error handling, redundancy management, and custom signaling profiles to facilitate reliable and efficient Simulcrypt headend implementation.
This document provides implementation guidelines for the DVB Simulcrypt standard. It describes the architecture and protocols involved in simulcrypt systems, including the ECMG protocol between the security client system and conditional access modules, and the EMMG/PDG protocol between conditional access modules and multiplex equipment. The document outlines differences between version 1 and 2 of the standards, and provides recommendations for compliance. It also includes detailed state diagrams and descriptions of the protocols involved.
This document discusses digital set-top boxes (STBs) and related standards. It covers:
1) The DVB standards for digital TV broadcasting via different transmission media, including DVB-T for terrestrial, DVB-S for satellite, and DVB-C for cable. These share source coding/compression and service multiplexing standards.
2) STBs will be needed until integrated digital TVs are cheaper. Affordable STBs are key for digital TV adoption. Common standards help lower STB costs through economies of scale.
3) "Open architecture" and "interoperability" mean the STB functionality is defined by public standards and can receive services across networks, respectively. The
1) The document discusses quantization and pulse code modulation (PCM) in voice signal encoding. PCM assigns 256 possible values to digitally represent analog voice samples, divided into chords and steps on a linear scale.
2) A logarithmic quantization scale is better than a linear one for voice signals, as it allocates more quantization steps to lower amplitudes prevalent in speech. This "compressed encoding" improves fidelity.
3) Quantization error occurs when samples with different amplitudes are assigned the same digital value, distorting the reconstructed waveform. Compression helps maintain a higher signal-to-noise ratio especially for low amplitudes.
DVB-S2 is the second-generation specification for satellite broadcasting developed by DVB in 2003. It uses more advanced channel coding (LDPC codes) and modulation formats (QPSK, 8PSK, 16APSK, 32APSK) for a 30% increase in transmission capacity over DVB-S. DVB-S2 allows for adaptive coding and modulation to optimize transmission for each user. It is designed for broadcast, interactive, and professional applications with flexibility to handle different transponder characteristics and content formats.
The STi7167 is an integrated system-on-chip that combines a configurable DVB-T or DVB-C demodulator with STB decoding and display functions. It provides advanced HD and SD video decoding, audio decoding, graphics processing, and connectivity options. The chip's integrated features allow for low cost and small size STB designs for cable or terrestrial networks.
The document discusses DCT/IDCT concepts and applications. It provides an introduction to DCT and IDCT, explaining that they are used widely in video and audio compression. It describes the DCT and IDCT functions and how they work to transform signals between spatial and frequency domains. Examples of one-dimensional and two-dimensional DCT/IDCT equations are also given. Finally, common applications of DCT/IDCT compression techniques are listed, such as in DVD players, cable TV, graphics cards, and medical imaging systems.
The document provides an overview of MPEG-4, a standard that offers both advanced audio and video codecs as well as tools for combining multimedia such as audio, video, graphics and interactivity. It was developed through an open international process to select the best technologies. MPEG-4 codecs like AVC and AAC provide high compression efficiency, having been adopted for HDTV, mobile video, and digital music. Its rich media tools allow interactive experiences combining different media types.
DVB-S2 is the second-generation specification for satellite broadcasting developed by DVB in 2003. It uses more advanced channel coding (LDPC codes) and modulation formats (QPSK, 8PSK, 16APSK, 32APSK) for improved transmission performance, achieving up to a 30% increase in capacity over DVB-S. DVB-S2 allows for backwards compatibility with DVB-S receivers and uses adaptive coding and modulation to optimize transmission for different users and conditions. It provides high flexibility to work with different input streams, modulation schemes, and satellite transponder characteristics.
This document discusses service information (SI) in DVB systems, specifically the discontinuity information section. It provides packet syntax diagrams for an MPEG-2 transport stream, the network information section, service description section, and bouquet association section, which are used to deliver metadata about available TV and radio channels and services. It also includes the syntax for a discontinuity information section, which is used to signal discontinuities in MPEG program streams that are caused by operations like splicing.
This document provides an overview of satellite communications fundamentals. It discusses how satellites provide capabilities not available through landlines, such as mobility and quick implementation. However, satellites are not always the most cost effective solution due to limited frequency spectrum and spatial capacity. The document describes different types of satellite services and configurations, including geostationary and non-geostationary satellites. It also covers topics like frequency reuse, earth station antennas, and satellite link delays.
ATI Courses Satellite Communications Systems Engineering Professional Develop...Jim Jenkins
ATI Courses Satellite Communications Systems Engineering course sampler. This three-day course is designed for satellite communications engineers, spacecraft engineers, and managers who want to obtain an understanding of the "big picture" of satellite communications. Each topic is illustrated by detailed worked numerical examples, using published data for actual satellite communications systems. The course is technically oriented and includes mathematical derivations of the fundamental equations. It will enable the participants to perform their own satellite link budget calculations. The course will especially appeal to those whose objective is to develop quantitative computational skills in addition to obtaining a qualitative familiarity with the basic concepts.
The document provides implementation guidelines for using the DVB Simulcrypt standard, including describing the architecture and protocols, clarifying differences between protocol versions, explaining state diagrams and error handling, and providing recommendations for redundancy management between system components. It aims to facilitate reliable implementation of the DVB Simulcrypt model and interoperable interfaces between conditional access systems.
This document provides implementation guidelines for the DVB Simulcrypt standard. It describes the architecture and protocols involved in simulcrypt systems, including the ECMG protocol between the security client system and conditional access modules, and the EMMG/PDG protocol between conditional access modules and multiplex equipment. The document outlines differences between version 1 and 2 of the standards, and provides recommendations for compliance. It also includes detailed state diagrams and descriptions of the protocols to clarify permissible messages in each state.
This document provides implementation guidelines for the DVB Simulcrypt standard. It describes the architecture and protocols involved in simulcrypt systems, including the ECMG protocol between the security client system and conditional access modules, and the EMMG/PDG protocol between conditional access modules and multiplex equipment. The document outlines differences between version 1 and 2 of the standards, and provides recommendations for compliance. It also includes detailed state diagrams and descriptions of the protocols to clarify permissible messages in each state.
This document provides specifications for Service Information (SI) in Digital Video Broadcasting (DVB) systems. It defines the SI table mechanisms and tables used to describe services, events and other data in DVB transport streams. Section 5 describes the SI table system, including the mapping of sections into transport stream packets and coding of table identifiers. Section 6 defines various descriptors used within the SI tables to provide metadata about services, components, events and other data elements in DVB systems.
This document provides specifications for Service Information (SI) in Digital Video Broadcasting (DVB) systems. It defines the SI table mechanisms and tables used to describe services, events and other data in DVB transport streams. Section 5 describes the SI table system, including the mapping of sections into transport stream packets and coding of table identifiers. Section 6 defines various descriptors used within the SI tables to provide metadata about services, components, events and other data elements in DVB systems.
This document provides a specification for Service Information (SI) in Digital Video Broadcasting (DVB) systems. It defines the SI data tables and descriptors that are used to describe DVB services, events, and other data elements. The SI tables include the Network Information Table (NIT), Bouquet Association Table (BAT), Service Description Table (SDT), Event Information Table (EIT), Time and Date Table (TDT), Time Offset Table (TOT), Running Status Table (RST), Stuffing Table (ST), and Discontinuity Information Table (DIT). The document also specifies over 50 descriptors that provide additional metadata about services, components, events, content, ratings, and other attributes.
This document provides a specification for Service Information (SI) in Digital Video Broadcasting (DVB) systems. It defines the SI data tables and descriptors that are used to describe content, events, and services in DVB systems. The document specifies the SI table mechanism, table definitions, descriptor identification and coding. It also defines Storage Media Interoperability measures for SI implementation on removable storage media.
This document provides specifications for Service Information (SI) in Digital Video Broadcasting (DVB) systems. It defines the SI table mechanisms and tables used to describe services, events and other data in DVB transport streams. Section 5 describes the SI table system, including the mapping of sections into transport stream packets and coding of table identifiers. Section 6 defines various descriptors used within the SI tables to provide metadata about services, components, events and other data elements in DVB systems.
This document provides specifications for Service Information (SI) in Digital Video Broadcasting (DVB) systems. It defines the SI table mechanisms and tables used to describe services, events and other data in DVB transport streams. Section 5 describes the SI table system, including the mapping of sections into transport stream packets and coding of table identifiers. Section 6 defines various descriptors used to provide additional information about services, components, events, etc. The document contains specifications for Network Information Table, Bouquet Association Table, Service Description Table, Event Information Table and other tables.
This document provides the European standard for the frame structure, channel coding, and modulation for a second generation digital transmission system for cable systems (DVB-C2). It defines the system architecture and target performance, as well as the input processing including mode adaptation, stream adaptation, and bit-interleaved coding and modulation for DVB-C2. The standard specifies the input formats, outer encoding using BCH, inner encoding using LDPC, bit interleaving, and mapping of bits onto constellations.
This document provides the European standard for the frame structure, channel coding and modulation for a second generation digital transmission system for cable systems (DVB-C2). It defines the system architecture and specifications for input processing, bit-interleaved coding and modulation, data slice packet generation, layer 1 part 2 signalling, frame building, and OFDM generation. The standard aims to provide improved performance for cable systems over the existing DVB-C standard.
This document provides the European standard for the frame structure, channel coding and modulation for a second generation digital transmission system for cable systems (DVB-C2). It defines the system architecture and specifications for input processing, bit-interleaved coding and modulation, data slice packet generation, layer 1 part 2 signalling, frame building, and OFDM generation. The standard aims to provide improved performance for cable systems over the existing DVB-C standard.
This document provides the European standard for the frame structure, channel coding, and modulation for a second generation digital transmission system for cable systems (DVB-C2). It defines the system architecture and target performance, as well as the input processing including mode adaptation, stream adaptation, and bit-interleaved coding and modulation for DVB-C2. The standard specifies the input formats, outer encoding using BCH, inner encoding using LDPC, bit interleaving, and mapping of bits onto constellations.
This document provides a European standard for a second generation digital transmission system for cable systems, known as DVB-C2. It defines the system architecture, input processing, bit-interleaved coding and modulation, data slice packet generation, layer 1 part 2 signalling generation and coding, frame builder functions, and OFDM generation for the DVB-C2 system. The standard specifies the frame structure, coding, modulation, and other technical aspects to enable digital video and audio broadcasting over cable networks.
This document provides the European standard for the frame structure, channel coding and modulation for a second generation digital transmission system for cable systems (DVB-C2). It defines the system architecture and specifications for input processing, bit-interleaved coding and modulation, data slice packet generation, layer 1 part 2 signalling, frame building, and OFDM generation. The standard aims to provide improved performance for cable systems over the existing DVB-C standard.
This document provides specifications for a digital video broadcasting (DVB) interaction channel for cable TV distribution systems (CATV). It defines a reference model and protocol stack for narrowband interaction channels to support asymmetric interactive services. The specification defines the physical layer, framing, medium access control (MAC) functionality, and mid-layer protocols for the interaction channel. Key aspects include the use of out-of-band and in-band signaling, TDMA multiple access, MAC messages for initialization, connection establishment, and link management, and optional security measures. The specification aims to enable interactive services for cable TV networks using DVB technology.
This document provides specifications for a digital video broadcasting (DVB) interaction channel for cable TV distribution systems (CATV). It defines a reference model and protocol stack for narrowband interaction channels to support asymmetric interactive services. The specification defines the physical layer, framing, medium access control (MAC) functionality, and mid-layer protocols for the interaction channel. Key aspects include the use of out-of-band and in-band signaling, TDMA multiple access, MAC messages for initialization, connection establishment, and link management, and optional security measures. The specification aims to enable interactive services for cable TV networks using DVB technology.
This document provides specifications for a digital video broadcasting (DVB) interaction channel for cable TV distribution systems. It defines a reference model for the system architecture and protocol stack for narrowband interaction channels to support asymmetric interactive services. It then specifies the DVB interaction channel for CATV networks, including the system concept with out-of-band/in-band principles, spectrum allocation, and FDM/TDMA multiple access. It also defines the lower physical layer specifications for the forward and return interaction paths, including modulation, framing, and other channel coding parameters.
This document provides specifications for using video and audio coding in digital broadcasting applications based on the MPEG-2 Transport Stream. It covers systems layer aspects like transport streams, transport stream packets, adaptation fields, and packetized elementary stream packets. The document defines requirements for baseline IRDs (integrated receiver decoders) and specifies fields in the transport packet and PES packet headers.
This document provides specifications for digital video and audio coding in broadcasting applications using MPEG-2 and H.264/AVC video coding and MPEG-1 Layer 2, MPEG-1 Layer 3 (MP3), MPEG-4, AC-3, Enhanced AC-3, DTS, AAC, and MPEG HEAAC audio coding based on the MPEG-2 transport stream. It defines requirements for IRDs and bitstreams for standard and high definition television at frame rates of 25 Hz, 30 Hz and 50 Hz. The document covers systems layer, video, audio, and synchronization specifications that are common to all IRDs and bitstreams.
The Event Logger monitors and logs Digital Program Insertion (DPI) messages to verify correct transmission of signals via satellite. It watches for configured GPI state changes that indicate an expected DPI message. If the message is received on time, it is logged as a matched event. If not received on time, it is flagged as missed. The Event Logger also decodes DPI messages to help diagnose issues, and is compatible with various encoding systems. It has 6 ASI inputs, 108 GPI sensors, and logs data in real-time and for archiving.
Euler's theorem states that for any plane graph, the number of vertices (v) minus the number of edges (e) plus the number of faces (f) equals 2. The document proves this theorem by considering a minimal tree (T) within the graph and its dual tree (D), showing that the number of edges of T and D sum to the total edges (e) of the original graph. Some applications of the theorem are that any plane graph contains an edge of degree 5 or higher and any finite set of points not all on a line contains a line with exactly two points.
This document provides an overview of satellite communications fundamentals. It discusses how satellites provide capabilities not available through landlines, such as mobility and quick implementation. However, satellites are not always the most cost effective solution due to limited frequency spectrum and spatial capacity. The document describes different types of satellite services and configurations, including geostationary and non-geostationary satellites. It also covers topics like frequency reuse, earth station antennas, and satellite link delays.
The document discusses quantization in analog-to-digital conversion. It describes the three processes of A/D conversion as sampling, quantization, and binary encoding. Quantization involves mapping amplitude values into a set of discrete values using a quantization interval or step size. The document discusses uniform quantization and how the quantization levels are determined. It also covers non-uniform quantization and provides examples and MATLAB code demonstrations of audio signal quantization.
This document discusses Euler's formula, which relates the number of vertices (V), edges (E), and faces (P) of a polyhedron. Through experimenting with attaching polygons and bending shapes, students derive the formula V - E + P = 2 for polyhedra. Removing a face shows the formula still holds, revealing why it is true for any polyhedron. Students learn the formula can distinguish polyhedra from other 3D shapes by calculating the Euler characteristic V - E + P.
This document provides an introduction to Reed-Solomon codes, which are word-oriented, non-binary BCH codes that are simple, robust, and perform well for burst errors. Reed-Solomon codes use Galois field techniques to encode data into blocks of length 2^m - 1 by adding 2t parity check words, allowing the correction of t errors. The encoding and decoding procedures make use of a generator polynomial, Berlekamp-Massey algorithm, Chien search, and Forney algorithm. Future work may include more flexible generator polynomials or converting C54x codes to C55x codes.
This document provides a 3-sentence summary of the given document on video compression:
The document discusses video compression algorithms used in standards like MPEG, explaining how video compression works through motion estimation, discrete cosine transformation, quantization, and entropy coding to reduce file sizes. It analyzes the tradeoff between compression ratio and quality, and provides details on common video compression standards and their applications. The MPEG standards are described in particular detail, outlining the different frame types and compression steps used to remove spatial and temporal redundancies from video for more efficient storage and transmission.
This document provides an overview of the Linux operating system and fundamentals for learning Linux, including:
- Details on Linux distributions like Debian, Red Hat, and SUSE and their licensing models.
- A brief history of open source software development and benefits of the open source model.
- How to log into a Linux system, basics of the shell, command line navigation, and file management.
- Key topics covered include files/directories, permissions, and redirection.
- Information on Linux certification programs.
- Setup instructions for a Linux emulator for the fundamentals course.
This document discusses three methods for reducing bitrates in digital video transmission: time-shifting MPEG-2 packets, open loop transrating, and closed loop transrating. Time-shifting involves advancing or delaying packets to smooth out variable bitrates, while open loop transrating re-quantizes video frames without feedback. Closed loop transrating also re-quantizes but uses error detection and feedback loops to learn from previous frames and optimize re-quantization levels, allowing for greater bitrate reductions than open loop. These methods aim to more efficiently use bandwidth and enable network operators to provide more video services over existing infrastructure.
This document provides a beginner's guide to learning Linux. It covers topics such as what Linux is, understanding files and folders, users and permissions, the root user, opening a terminal, basic commands like ls, cd, pwd, and tar for archiving files. The guide explains important Linux concepts and provides examples of common commands to get started using the Linux command line.
The RS-232 interface is a standard for serial binary data interchange between devices. It allows up to 20 signals but only requires 3 wires: send data, receive data, and signal ground. Communication uses asynchronous transmission of start bits, data bits, optional parity bits, and stop bits. The standard connector has 25 pins but many signals are unnecessary for direct computer-terminal connections. RS-232 specifies voltage levels for logic 1 and 0 signals and establishes compatibility but not communication between compliant devices.
The document discusses digital set-top boxes (STBs) and open architecture/interoperability issues. It provides details on:
1) International digital TV standards DVB-T, DVB-S, DVB-C and how STBs can receive all three signals with switchable front ends.
2) The DVB Common Interface standard which allows a STB to be interoperable across different networks using different conditional access systems via external modules.
3) The Multimedia Home Platform standard which seeks to create an open middleware based on Java, allowing for interoperable applications across networks.
This document specifies how to encapsulate MPEG-2 Transport Stream data within DAB MSC stream data sub-channels, including adding error protection. It describes using Reed-Solomon coding and interleaving to provide outer coding and error protection. The document references ETSI EN 300 401 for information on the DAB radio broadcasting system.
Things to Consider When Choosing a Website Developer for your Website | FODUUFODUU
Choosing the right website developer is crucial for your business. This article covers essential factors to consider, including experience, portfolio, technical skills, communication, pricing, reputation & reviews, cost and budget considerations and post-launch support. Make an informed decision to ensure your website meets your business goals.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
CAKE: Sharing Slices of Confidential Data on BlockchainClaudio Di Ciccio
Presented at the CAiSE 2024 Forum, Intelligent Information Systems, June 6th, Limassol, Cyprus.
Synopsis: Cooperative information systems typically involve various entities in a collaborative process within a distributed environment. Blockchain technology offers a mechanism for automating such processes, even when only partial trust exists among participants. The data stored on the blockchain is replicated across all nodes in the network, ensuring accessibility to all participants. While this aspect facilitates traceability, integrity, and persistence, it poses challenges for adopting public blockchains in enterprise settings due to confidentiality issues. In this paper, we present a software tool named Control Access via Key Encryption (CAKE), designed to ensure data confidentiality in scenarios involving public blockchains. After outlining its core components and functionalities, we showcase the application of CAKE in the context of a real-world cyber-security project within the logistics domain.
Paper: https://doi.org/10.1007/978-3-031-61000-4_16
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
DVBSimulcrypt2
1. TS 101 197-1 V1.1.1 (1997-06)
Technical Specification
Digital Video Broadcasting (DVB);
DVB SimulCrypt;
Part 1: Head-end architecture and synchronization
European Broadcasting Union Union Européenne de Radio-Télévision
5. 5 TS 101 197-1 V1.1.1 (1997-06)
8.4 Play-out issues ................................................................................................................................................. 38
8.4.1 ECMs ......................................................................................................................................................... 38
8.4.2 EMMs and private data .............................................................................................................................. 39
8.5 Event realignment ............................................................................................................................................ 39
9 System layering......................................................................................................................................39
9.1 Introduction...................................................................................................................................................... 39
9.2 Physical Layer.................................................................................................................................................. 39
9.3 Data Link Layer ............................................................................................................................................... 39
9.4 Network Layer ................................................................................................................................................. 40
9.5 Transport Layer ............................................................................................................................................... 40
9.6 Session Layer................................................................................................................................................... 40
9.7 System layering overview/Communications protocol stack............................................................................. 41
9.8 TCP connection establishment......................................................................................................................... 41
Annex A (informative): SCS coexistence..............................................................................................42
A.1 Introduction............................................................................................................................................42
A.2 Example scenario ...................................................................................................................................42
Annex B (informative): Control Word (CW) generation and testing ...............................................43
B.1 Introduction............................................................................................................................................43
B.2 Background ............................................................................................................................................43
B.3 Generation..............................................................................................................................................43
B.4 Control Word (CW) randomness verification testing............................................................................44
B.4.1 Bias 1/0 ............................................................................................................................................................ 44
B.4.2 Auto-correlation............................................................................................................................................... 44
B.5 Testing locations ....................................................................................................................................44
History ..............................................................................................................................................................45
6. 6 TS 101 197-1 V1.1.1 (1997-06)
Intellectual Property Rights
ETSI has not been informed of the existence of any Intellectual Property Right (IPR) which could be, or could become
essential to the present document. However, pursuant to the ETSI Interim IPR Policy, no investigation, including IPR
searches, has been carried out. No guarantee can be given as to the existence of any IPRs which are, or may be, or may
become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by the Joint Technical Committee (JTC) of the European
Broadcasting Union (EBU), Comité Européen de Normalisation ELECtrotechnique (CENELEC) and the European
Telecommunications Standards Institute (ETSI).
NOTE: The EBU/ETSI JTC was established in 1990 to co-ordinate the drafting of ETSs in the specific field of
broadcasting and related fields. Since 1995 the JTC became a tripartite body by including in the
Memorandum of Understanding also CENELEC, which is responsible for the standardization of radio and
television receivers. The EBU is a professional association of broadcasting organizations whose work
includes the co-ordination of its Members' activities in the technical, legal, programme-making and
programme-exchange domains. The EBU has active members in about 60 countries in the European
Broadcasting Area; its headquarters is in Geneva *.
* European Broadcasting Union
Case Postale 67
CH-1218 GRAND SACONNEX (Geneva)
Switzerland
Tel: +41 22 717 21 11
Fax: +41 22 717 24 81
Digital Video Broadcasting (DVB) Project
Founded in September 1993, the DVB Project is a market-led consortium of public and private sector organizations in
the television industry. Its aim is to establish the framework for the introduction of MPEG-2 based digital television
services. Now comprising over 200 organizations from more than 25 countries around the world, DVB fosters
market-led systems, which meet the real needs, and economic circumstances, of the consumer electronics and the
broadcast industry.
7. 7 TS 101 197-1 V1.1.1 (1997-06)
1 Scope
This Technical Specification (TS) is part 1 of a multi-part document covering Digital Video Broadcasting (DVB);
DVB SimulCrypt, as identified below:
Part 1: "Head-end architecture and synchronization";
Part 2: "Extended interoperability and control".
Parts 1 and 2 together address the requirements for interoperability between two or more Conditional Access (CA)
systems at a head-end.
Part 1: specifies the system architecture, timing relationships and messaging structures; and
Part 2: specifies extended interoperability and control.
The components within the system architecture represent functional units. The boundaries between physical units are not
required to match the boundaries between functional units. It is possible that the SimulCrypt Synchronizer (SCS) could
be in the Multiplexer (MUX) or the SCS and MUX could be built independently. Neither architecture is mandated.
1.1 Common scrambling algorithm
The DVB SimulCrypt system is based on the concept of a shared scrambling and descrambling method. No problems
were noted so far on the possible constraints which the DVB SimulCrypt architecture might impose on the use of a
shared scrambling and descrambling method.
1.2 Language
The word "shall" is used in a normative statement that can be verified and is normative/mandatory. The word "should" is
used in the context of a recommendation/option or a statement that cannot be verified or it is not normative/mandatory.
2 Normative references
References may be made to:
a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in
which case, subsequent revisions to the referenced document do not apply; or
b) all versions up to and including the identified version (identified by "up to and including" before the version
identity); or
c) all versions subsequent to and including the identified version (identified by "onwards" following the version
identity); or
d) publications without mention of a specific version, in which case the latest version applies.
A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ISO/IEC 13818-1 (1994): "Information Technology - Generic Coding of Moving Pictures and
Associated Audio Recommendation H.222.0 (Systems)".
[2] ETS 300 468: "Digital Video Broadcasting (DVB); Specification for Service Information (SI) in
DVB systems".
[3] ETR 162: "Digital Video Broadcasting (DVB); Allocation of Service Information (SI) codes for
DVB systems".
8. 8 TS 101 197-1 V1.1.1 (1997-06)
[4] ETR 289: "Digital Video Broadcasting (DVB); Support for use of scrambling and Conditional
Access (CA) within DVB systems".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following definitions apply:
broadcaster (service provider): An organization which assembles a sequence of events or services to be delivered to
the viewer based upon a schedule.
CA_system_id: Conditional Access (CA) System IDs are defined in table 3 "CA_system_ID" of ETR 162 [3].
CA_subsystem_ID: The CA_subsystem_ID is defined in the present document to handle multiple connections to
ECMGs with the same CA_system_ID value. The combination of CA_system_ID and CA_subsystem_ID is called
Super_CAS_ID.
CA components: Those components brought by a CA provider for integration into a host head-end system.
channel: An application specific representation of an open Transport Control Protocol (TCP) connection, allowing the
association of application specific parameters with such a connection. Channels correspond on a one to one basis to TCP
connections.
client: A software entity on a host making use of one or more resources offered by a server.
Conditional Access (CA) system: A system to control subscriber access to broadcast services and events e.g.
Videoguard, Eurocrypt.
Control Word (CW): A data object used for scrambling.
Control Word Generator (CWG): This component receives a CW request from the SimulCrypt Synchronizer (SCS)
and returns a CW.
Crypto Period (CP): The period when a particular Control Word (CW) is being used by the scrambler.
Entitlement Control Message (ECM): Private Conditional Access (CA) information which carries the CW in a secure
manner and private entitlement information.
Entitlement Control Message Generator (ECMG): This generator produces the ECM messages but does not support
ECM repetition. See subclause 4.2.3.
Entitlement Management Message (EMM): Private Conditional Access (CA) information which, for example,
specifies the authorization levels of subscribers or groups of subscribers for services or events.
Entitlement Management Message Generator (EMMG): This generator produces the EMM messages and repeatedly
plays them out at the appropriate times. See subclause 4.2.4.
forbidden: The term "forbidden" when used in the present document indicates that the value shall never be used.
generator: A component producing data.
host: A computer system uniquely identified by its Internet Protocol (IP) address, and as such addressable in a computer
network. It may take both client and server roles.
host head-end: A system which is composed of those components required before a CA provider can be introduced into
the head-end.
MPEG-2: Refers to the standard ISO/IEC 13818 [1]. Systems coding is defined in part 1. Video coding is defined in
part 2. Audio coding is defined in part 3.
multiplex: A stream of all the digital data within a single physical channel carrying one or more services or events.
9. 9 TS 101 197-1 V1.1.1 (1997-06)
Multiplexer (MUX): See subclause 4.2.10.
Private Data Generator (PDG): See subclause 4.2.5.
proprietary: This term details the fact that the interface will be specified by the head-end provider, or by the CA
provider. The interface can be commercially open but is not open within the present document. Its availability will be
via commercial/technical agreements.
reserved: The term "reserved" when used in the clause defining the coded bit stream, indicates that the value may be
used in the future for ISO defined extensions. Unless otherwise specified within the present document all "reserved" bits
shall be set to "1".
reserved future use: The term "reserved_future_use", when used in the clause defining the coded bit stream, indicates
that the value may be used in future for ETSI defined extensions. Unless otherwise specified within the present document
all "reserved_future_use" bits shall be set to "1".
resource: A set of coherent functions, accessible through a server. More than one resource can reside on a single host.
Scrambler (SCR): See subclause 4.2.11.
server: A software entity exporting a resource. More than one server may reside on a single host. A server is uniquely
identified by an Internet Protocol (IP) address and Transport Control Protocol (TCP) port number.
service: A sequence of events under the control of a broadcaster which can be broadcast as part of a schedule.
Service Information (SI): Information that is transmitted in the transport stream to aid navigation and event selection.
SI generator: See subclause 4.2.8.
SimulCrypt: "SimulCrypt" is a process that facilitates using several Conditional Access (CA) systems in parallel, in
conjunction with the DVB common scrambling algorithm, to control access to pay-TV services. SimulCrypt involves the
inter-operation of two or more CA streams in a DVB environment. The DVB SimulCrypt addresses specifically the
requirements for interoperability between two or more CA systems at a head-end.
SimulCrypt Synchronizer (SCS): The logical component that acquires CW, Entitlement Control Messages (ECM) and
synchronizes their play-out for all the CA systems connected.
stream: An independent bi-directional data flow across a channel. Multiple streams may flow on a single channel.
Stream_IDs (e.g. ECM_stream_ID, Data_stream_ID, etc.) are used to tag messages belonging to a particular stream.
Transport Stream (TS): A TS is a data structure defined in ISO/IEC 13818-1 [1]. It is the basis of DVB related
standards.
10. 10 TS 101 197-1 V1.1.1 (1997-06)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AC Access Criteria
ASCII American Standard Code for Information Interchange
bslbf bit string, left bit first
BW BandWidth
CA Conditional Access
CAT Conditional Access Table
CP Crypto Period
CPU Central Processing Unit
CRC Cyclic Redundancy Check
CW Control Word
CWG Control Word Generator
DNS Domain Name Server
DVB Digital Video Broadcasting
ECM Entitlement Control Message
ECMG Entitlement Control Message Generator
EIS Event Information Scheduler
EIT Event Information Table
EMM Entitlement Management Message
EMMG Entitlement Management Message Generator
ID Identifier
IP Internet Protocol
ISO International Organization for Standardization
LSB Least Significant Bit
MJD Modified Julian Date
MPEG Moving Pictures Expert Group
MSB Most Significant Bit
MUX Multiplexer
NIT Network Information Table
OSI Open Systems Interconnect
PAT Program Association Table
PDG Private Data Generator
PID Packet Identifier
PMT Program Map Table
PSI Program Specific Information
RFC Request For Comment
SCR (DVB compliant) Scrambler
SCS SimulCrypt Synchronizer
SDT Service Description Table
SI Service Information
SIG Service Information Generator
SMS Subscriber Management System
ST Stuffing Table
STB Set Top Box
tcimsbf two's complement integer MSB (sign) bit first
TCP Transport Control Protocol
TDT Time and Date Table
TLV Type, Length, Value
TS Transport Stream
UDP User Datagram Protocol
uimsbf unsigned integer most significant bit first
UTC Universal Time, Co-ordinated
11. 11 TS 101 197-1 V1.1.1 (1997-06)
4 Architecture
4.1 System architecture
Figure 1 shows the logical relationships between the components and which component-to-component interfaces are
defined in the present document. Other components exist in a head-end which are not illustrated in Figure 1 i.e. SMS.
PDG 2
PDG 1
EMMG 2
EMMG 1
Multiplexer
Scrambler
SI Gen
Custom SI 2
Custom SI 1
EIS
PSI Gen
Mux Config
ECMG 2
Simulcrypt
ECMG 1 Sync
Defined in this document
In scope - Part 2
Out of scope
Simlucrypt CA components
CWG Host head-end components
Figure 1: System architecture
The DVB SimulCrypt system architecture illustrated above is divided into two areas:
4.1.1 Host head-end components
Host head-end components are those that will need to exist before SimulCrypt CA components can be introduced into a
DVB SimulCrypt head-end.
4.1.2 SimulCrypt CA components
SimulCrypt CA components are typically those which are brought by a new CA provider to introduce his CA into a
DVB SimulCrypt head-end.
NOTE: The EMMGs, PDGs and custom SI generators are not necessarily required in a DVB SimulCrypt system.
12. 12 TS 101 197-1 V1.1.1 (1997-06)
4.2 Description of components
4.2.1 Event Information Scheduler (EIS)
In the DVB SimulCrypt system architecture diagram (subclause 4.1), the EIS is the functional unit in charge of holding
all the schedule information, all the configurations and CA specific information required for the complete system. It is
the overall database store for the whole head-end system. For instance, it is in charge of providing to the ECMGs (via
the SCS) any information they need to generate their ECMs.
In reality this function might be distributed over several physical units, storage locations, and/or input terminals, and it
may communicate with any other functional unit of the architecture diagram.
Concerning the CA provider components, the connections to the EIS and the data they carry will be agreed through the
commercial arrangements made with the broadcaster. They are not defined in the present document.
4.2.2 SimulCrypt Synchronizer (SCS)
The role of the SimulCrypt Synchronizer (SCS) is to:
- establish TCP connections with ECMGs and set-up one channel per connection;
- set-up streams within channels as needed and allocate ECM_stream_ID values;
- get the CWs from the CWG;
- supply the CWs to the relevant ECMGs on the relevant streams, as well as any CA specific information;
- acquire ECMs from the ECMGs;
- synchronize the ECMs with their associated CPs according to channel parameters;
- submit these ECMs to the MUX and request their repetition according to the channel parameters;
- supply the CW to the scrambler for use in the specified CP.
4.2.3 Entitlement Control Message Generator (ECMG)
The ECMG shall receive CWs in a CW provision message as well as access criteria and shall reply with an ECM or an error
message. The ECMG does not support ECM repetition.
4.2.4 Entitlement Management Message Generator (EMMG)
This component, supplied by the CA provider shall interface over a DVB SimulCrypt specified interface to the MUX.
The EMMG initiates connections to the MUX.
4.2.5 Private Data Generator (PDG)
This component is shown in the DVB SimulCrypt system architecture diagram (figure 1) to highlight the fact that the
EMMG to MUX interface can be used for EMM's and other CA related private data. The PDG initiates connections to
the MUX.
4.2.6 Custom Service Information Generator (SIG)
This component is responsible for generating private SI. It interfaces to both the SI and PSI generators. These interfaces
are not defined by the present document.
13. 13 TS 101 197-1 V1.1.1 (1997-06)
4.2.7 Multiplexer configuration (MUX Config)
This component is responsible for configuring the MUX and providing a link to the Program Specific Information (PSI)
generator for PSI construction and play-out. The interfaces "MUX Config and MUX" and "MUX Config and PSI
Generator" are not defined by the present document.
4.2.8 SI generator
This component is responsible for generating the SI (see ETS 300 468 [2]) for the system. The SI server takes its
primary data from the EIS and supplementary data from the Custom SI servers supplied by the CA providers. The
interfaces between the EIS and SI Server, and SI Server and MUX are not defined by the present document.
4.2.9 Program Specific Information (PSI) generator
This component is responsible for generating the PSI (see ISO/IEC 13818-1 [1]) for the system. The PSI server takes its
primary data from MUX Config and supplementary data from the Custom SI servers supplied by the CA providers.
4.2.10 Multiplexer (MUX)
The role of this head-end component is to perform time multiplexing of input data, and to output an MPEG-2 Transport
Stream (TS). The input data can be transport packets, MPEG sections or raw data. The exact functionality of a MUX is
implementation specific. For the purpose of the present document, the MUX shall be able to communicate with the
SimulCrypt Synchronizer (SCS), and to accept connections with Entitlement Management Message Generators
(EMMG) with the interface defined.
4.2.11 Scrambler (SCR)
The related interfaces are not defined by the present document.
4.2.12 Control Word Generator (CWG)
The related interfaces are not defined by the present document.
5 Description of interfaces
5.1 ECMG <> SCS
5.1.1 Channel specific messages
These messages are defined further in subclause 7.1.3. This interface shall carry the following channel messages:
- Channel_setup;
- Channel_test;
- Channel_status;
- Channel_close;
- Channel_error.
14. 14 TS 101 197-1 V1.1.1 (1997-06)
5.1.2 Stream specific messages
These messages are defined further in subclause 7.1.4. The interface shall carry the following stream messages:
- Stream_setup;
- Stream_test;
- Stream_status;
- Stream_close_request;
- Stream_close_response;
- Stream_error;
- CW_provision;
- ECM_response.
5.1.3 Interface principles
For this interface, the SCS is the client and the ECMG is the server. The SCS has a prior knowledge of the mapping
between Super_CAS_IDs and the IP addresses and port numbers of the ECMGs. When a new ECM stream is requested
by the EIS for a given Super_CAS_ID value, the SCS will open a new stream with the appropriate ECMG. This might
require the opening of a new channel (which involves the opening of a new TCP connection).
NOTE: There can be several ECMGs associated with the same Super_CAS_ID value (e.g. for performance or
redundancy reasons). In such a case the SCS should be able to chose with which ECMG the connection
will be opened based on either a redundancy policy or resource available.
5.1.3.1 Channel establishment
There is always one (and only one) channel per TCP connection. Once the TCP connection is established, the SCS sends
a Channel_setup message to the ECMG. In case of success the ECMG replies by sending back a Channel_status
message.
In case of a rejection or a failure during channel set-up the ECMG replies with a Channel_error message. This means
that the channel has not been opened by the ECMG and the SCS shall close the TCP connection.
5.1.3.2 Stream establishment
The SCS sends a Stream_setup message to the ECMG. In case of success the ECMG replies by sending back a
Stream_status message. In case of a rejection or a failure the ECMG replies with a Stream_error message.
Once the connection, channel and stream have been correctly established the ECM will be transferred. It can be
transferred as sections or as TS packets. The ECMG indicates at channel set-up which kind of data object will be used.
Once the connection, channel and stream have been correctly established, ECMs will be transferred to the SCS as a
response to the CW_provision message.
5.1.3.3 Stream closure
Stream closure is always initiated by the SCS. This can occur when an ECM stream is no longer needed or in the case of
an error. This is done by means of a Stream_close_request message. A stream_close_response message indicates the
stream has been closed.
5.1.3.4 Channel closure
Channel closure can occur when the channel is no longer needed or in case of error (detected by SCS or reported by
ECMG). This is done by means of a Channel_close message sent by the SCS. Subsequently, the connection shall be
closed by both sides.
15. 15 TS 101 197-1 V1.1.1 (1997-06)
5.1.3.5 Channel/Stream testing and status
At any moment either component can send a Channel_test/Stream_test message to check the integrity of a
channel/stream. In response to this message the receiving component shall reply with either a channel/stream status
message or a channel/stream error message.
5.1.3.6 Unexpected communication loss
Both SCS and ECMG shall be able to handle an unexpected communication loss (either on the connection, channel or
stream level).
Each component, when suspecting a possible communication loss (e.g. a 10-second silent period), should check the
communication status by sending a test message and expecting to receive a status message. If the status message is not
received in a given time (implementation specific) the communication path should be re-established.
5.1.3.7 Handling data inconsistencies
If the ECMG detects an inconsistency it shall send an error message to the SCS. If the SCS receives such a message or
detects an inconsistency it may close the connection. The SCS (as the client) will then (re-)establish the connection,
channel and (if applicable) streams.
NOTE: The occurrence of a user defined or unknown parameter_type or message_type shall not be considered as
an inconsistency.
5.2 EMMG <> MUX
5.2.1 Channel specific messages
These messages are defined further in subclause 7.2.3. The interface shall carry the following channel messages:
- Channel_setup
- Channel_test
- Channel_status
- Channel_close
- Channel_error
5.2.2 Stream specific messages
These messages are defined further in subclause 7.2.4. The interface shall carry the following stream messages:
- Stream_setup;
- Stream_test;
- Stream_status;
- Stream_close_request;
- Stream_close_response;
- Stream_error;
- Data_provision.
5.2.3 Interface principles
For this interface, the EMMG is the client and the MUX is the server.
16. 16 TS 101 197-1 V1.1.1 (1997-06)
5.2.3.1 Channel establishment
The EMMG sends a Channel_setup message to the MUX. In case of success the MUX replies by sending back a
Channel_status message.
In case of a rejection or a failure during channel set-up the MUX replies with a Channel_error message. This means that
the channel has not been opened by the MUX and the EMMG shall close the TCP connection.
5.2.3.2 Stream establishment
The EMMG sends a Stream_setup message to the MUX. In case of success the MUX replies by sending back a
Stream_status message. In case of a rejection or a failure the MUX replies with a Stream_error message.
Once the connection, channel and stream have been correctly established the EMM will be transferred. It can be
transferred as sections or as TS packets. The EMMG indicates at channel set-up which kind of data object will be used.
5.2.3.3 Bandwidth allocation
The interface allows bandwidth negotiation between the EMMG and the MUX. This is not mandatory. During stream
set-up the EMMG will request the optimal bandwidth for that stream. The MUX will then respond with the bandwidth
that has been allocated for that stream. The EMMG can, at a later time, request an adjustment in the bandwidth
allocation. The MUX could also initiate an allocation change, without any request from the EMMG.
5.2.3.4 Stream closure
Stream closure is always initiated by the EMMG. This can occur when an EMM stream is no longer needed. This is
done by means of a Stream_close_request message. A stream_close_response message indicates the stream has been
closed.
5.2.3.5 Channel closure
Channel closure can occur when the channel is no longer needed or in case of error (detected by EMMG or reported by
MUX). This is done by means of a Channel_close message sent by the EMMG. Subsequently, the connection shall be
closed by both sides.
5.2.3.6 Channel/Stream testing and status
At any moment either component can send a Channel_test/Stream_test message to check the integrity of a
channel/stream. In response to this message the receiving component shall reply with either a channel/stream status
message or a channel/stream error message.
5.2.3.7 Unexpected connection loss
Both EMMG and MUX shall be able to handle an unexpected communication loss (either on the connection, channel or
stream level).
Each component, when suspecting a possible communication loss (e.g. a 10-second silent period), should check the
communication status by sending a test message and expecting to receive a status message. If the status message is not
received in a given time (implementation specific) the communication path should be re-established.
5.2.3.8 Handling data inconsistencies
If the MUX detects an inconsistency it shall send an error message to the EMMG. If the EMMG receives such a
message or detects an inconsistency it should close the connection. The EMMG (as the client) will then (re-)establish the
connection, channel and (if applicable) streams
NOTE: The occurrence of a user defined or unknown parameter_type or message_type shall not be considered as
an inconsistency.
17. 17 TS 101 197-1 V1.1.1 (1997-06)
5.3 PDG <> MUX
The interface used is the EMMG<>MUX interface.
5.4 Custom SI Generator <> PSI Generator
Proprietary, not defined by the present document.
5.5 Custom SI Generator <> SI Generator
Proprietary, not defined by the present document.
5.6 EIS <> SI Generator
Proprietary, not defined by the present document.
5.7 SI Generator <> MUX
Proprietary, not defined by the present document.
5.8 EIS <> MUX Config
Proprietary, not defined by the present document.
5.9 MUX Config <> PSI Generator
Proprietary, not defined by the present document.
5.10 PSI Generator <> MUX
Proprietary, not defined by the present document.
5.11 MUX <> SCR
Proprietary, not defined by the present document.
5.12 SCR onward
Proprietary, not defined by the present document.
5.13 SCS <> MUX
Proprietary, not defined by the present document.
5.14 SCS <> SCR
Proprietary, not defined by the present document.
18. 18 TS 101 197-1 V1.1.1 (1997-06)
5.15 SCS <> CWG
Proprietary, not defined by the present document.
5.16 EIS <> SCS
Proprietary, not defined by the present document.
6 Generic message description
6.1 Generic message structure
On all interfaces, the messages shall have the following generic structure:
generic_message
{
protocol_version 1 bytes
message_type 2 bytes
message_length 2 bytes
for (i=0; i < n; i++)
{
parameter_type 2 bytes
parameter_length 2 bytes
parameter_value <parameter_length> bytes
}
}
protocol_version: An 8-bit field identifying the protocol version. It shall have the value 0x01.
message_type: A 16-bit field identifying the type of the message. The list of message type values is defined in
subclause 6.2 Unknown message types shall be ignored by the receiving entity.
message_length: This 16-bit field specifies the number of bytes in the message immediately following the
message_length field.
parameter_type: This 16-bit field specifies the type of the following parameter. The list of parameter type values are
defined in the interface specific clauses of the present document. Unknown parameters shall be ignored by the receiving
entity. The data associated with that parameter will be discarded and the remaining message processed.
parameter_length: This 16-bit field specifies the number of bytes of the following parameter_value field.
parameter_value: This variable length field specifies the actual value of the parameter. Its semantics is specific to the
parameter type value.
20. 20 TS 101 197-1 V1.1.1 (1997-06)
7 Interface specific message description
7.1 ECMG <> SCS
7.1.1 Parameter_type values
Parameter_type value Parameter type Type/units Length (bytes)
0x0000 Reserved - -
0x0001 Super_CAS_ID uimsbf 4
0x0002 section_TSpkt_flag Boolean 1
0x0003 delay_start tcimsbf/ms 2
0x0004 delay_stop tcimsbf/ms 2
0x0005 transition_delay_start tcimsbf/ms 2
0x0006 transition_delay_stop tcimsbf/ms 2
0x0007 ECM_rep_period uimsbf/ms 2
0x0008 max_streams uimsbf 2
0x0009 min_CP_duration uimsbf/n × 100 ms 2
0x000A lead_CW uimsbf 1
0x000B CW_per_msg uimsbf 1
0x000C max_comp_time uimsbf/ms 2
0x000D access_criteria user defined variable
0x000E ECM_channel_ID uimsbf 2
0x000F ECM_stream_ID uimsbf 2
0x0010 nominal_CP_duration uimsbf/n × 100 ms 2
0x0011 access_criteria_transfer_mode Boolean 1
0x0012 CP_number uimsbf 2
0x0013 CP_duration uimsbf/n × 100 ms 2
0x0014 CP_CW_Combination --- 10 (2 + 8)
CP uimsbf 2
CW uimsbf 8
0x0015 ECM_datagram user defined variable
0x0016 to 0x006F DVB reserved DVB reserved DVB reserved
0x7000 Error_status see subclause 7.1.5 2
0x7001 Error_information user defined variable
0x7002 to 0x7FFF DVB reserved - -
0x8000 to 0xFFFF User defined
21. 21 TS 101 197-1 V1.1.1 (1997-06)
7.1.2 Parameter semantics
AC_delay_start: This parameter shall be used in place of the delay start parameter for the first CP following a change
in AC.
AC_delay_stop: This parameter shall be used in place of the delay stop parameter for the last CP preceding a change in
AC.
access_criteria: This parameter contains CA system specific information of undefined length and format, needed by the
ECMG to build an ECM. It can be, for example, a pointer to an access criterion in an ECMG data base, or a list of
relevant access criteria items in an encapsulated TLV format. This parameter contains the information related to the CP
indicated in the CW_provision message. The presence and contents of the access criteria parameter are the result of CA
system supplier requirements.
access_criteria_transfer_mode: This 1-byte parameter is a flag. If it equals 0, it indicates that the access_criteria
parameter is required in the CW_provision message only when the contents of this parameter changes. If it equals 1, it
indicates that the ECMG requires the access_criteria parameter be present in each CW_provision message.
Super_CAS_ID: The Super_CAS_ID is a 32-bit identifier formed by the concatenation of the CA_system_id (16 bit)
and the CA_subsystem_ID (16 bit). It shall identify uniquely a (set of) ECMG(s) for a given SCS, see subclause 5.1.
The CA_subsystem_ID is defined by the user, it is private.
CP_CW_combination: This 10-byte parameter is the concatenation of the CP number the CW is attached to and the
CW itself. The parity (odd or even) of the CP number is equal to the parity of the corresponding CW (see ETR 289 [4]).
CP_duration: This parameter indicates the actual duration of a particular CP for a particular stream when it differs
from the nominal_CP_duration value (see definition below).
CP_number: An identifier to a CP. This parameter indicates the CP number a message is attached to. This is relevant
for the following messages: CW_provision, and ECM_response.
CW_per_msg: The number of CWs needed by the ECMG per CW provision message. If this value is "y" and lead_CW
is "x", each CW provision message attached to CP "n" will contain all CWs from period (n + 1 + x-y) to period (n + x).
CWs are carried with their CP number by means of the CP_CW_combination parameter. In most existing CA systems
CW_per_msg is 1 or 2. See also lead_CW.
For example, if an ECMG requires the current and next CW to generate an ECM, it shall by definition specify at least
one lead_CW. However, since it may buffer its own CWs, it can set CW_per_msg to one. By doing this, it always
receives the CW for the next CP and accessing the CW for the current CP from memory (a previous provision message).
Alternatively, it may specify 2 CW_per_msg and have both CWs available at ECM generation time. This eliminates the
need for ECMG buffering and can be advantageous for a hot backup to take over, since each provision message includes
all CWs required.
An SCS shall minimally support CW_per_msg values 1 and 2.
delay_start: This signed integer represents the amount of time between the start of a CP, and the start of the
broadcasting of the ECM attached to this period. If it is positive, it means that the ECM shall be delayed with respect to
the start of the CP. If negative, it means that the ECM shall be broadcast ahead of this time. This parameter is
communicated by the ECMG to the SCS during the channel set-up.
delay_stop: This signed integer represents the amount of time between the end of a CP, and the end of the broadcasting
of the ECM attached to this period. If it is positive, it means that the end of the ECM broadcast shall be delayed with
respect to the end of the CP. If negative, it means that the ECM broadcast shall be ended ahead of time. This parameter
is communicated by the ECMG to the SCS during the channel set-up.
ECM_channel_ID: The ECM_channel_ID is allocated by the SCS and uniquely identifies an ECM channel across all
connected ECMGs.
ECM_datagram: The actual ECM message to be passed by the SCS to the MUX. It can be either a series of transport
packets (of 188-byte length) or an MPEG-2 section, according to the value of section_TSpkt_flag. The ECM datagram
can have a zero length meaning that there is no ECM to be broadcast for the CP. The ECM datagram shall comply with
ETR 289 [4].
22. 22 TS 101 197-1 V1.1.1 (1997-06)
ECM_rep_period: This integer represents the period in milliseconds for the repetition of data (e.g. ECMs).
ECM_stream_ID: This identifier uniquely identifies a ECM stream within a channel. It is allocated by the SCS prior to
stream set-up.
Error_status: See subclause 7.1.5.
Error_information: This optional parameter contains user defined data completing the information provided by
error_status. It can be an ASCII text or the parameter ID value of a faulty parameter for example.
lead_CW: The number of CWs required in advance to build an ECM. If this value is "x" the ECMG requires CWs up to
CP number "n + x" to build the ECM attached to CP "n". In most existing CA systems lead_CW is 0 or 1. See also
CW_per_msg.
For example, if the ECMG requires the current and next CW to generate an ECM, lead_CW would be 1. In other words,
it defines the most future CW required for ECM generation.
An SCS shall minimally support lead_CW values 0 and 1.
max_comp_time: This parameter is communicated by the ECMG to the SCS during channel set-up. It is the worst case
time needed by an ECMG to compute an ECM when all the streams in a channel are being used. This time is typically
used by the SCS to decide when to time-out on the ECM_response message. This value shall be lower than the
min_CP_duration parameter of the same Channel_status message.
max_streams: Maximum number of simultaneous opened streams supported by an ECMG on a channel. This parameter
is communicated from the ECMG to the SCS during the channel set-up. A value of 0 means that this maximum is not
known.
min_CP_duration: This parameter is communicated at channel set-up by the ECMG to the SCS to indicate the
minimum supported amount of time a CW shall be active before it can be changed. This value shall be greater than the
max_comp_time parameter of the same Channel_status message.
nominal_CP_duration: This parameter indicates the nominal duration of CPs for the particular stream. It means that all
the CPs related to this stream will have this duration, except for the purpose of event alignments and error handling.
Even in these exceptional cases, all the actual CPs shall have a duration greater than or equal to the
nominal_CP_duration. In addition, the nominal CP duration (chosen by SCS) shall be greater than or equal to:
a) all the min_CP_duration specified by the ECMGs during Channel_set-up;
b) all the max_comp_time values specified by the ECMGs during channel set-up, plus typical network latencies.
section_TSpkt_flag: A value of "0" shall indicate that the ECM carried on the interface is in MPEG-2 section format.
A value of "1" shall indicate that these datagrams are in MPEG-2 transport stream packet format.
transition_delay_start: This parameter shall be used in place of the delay start parameter for the first CP following a
clear to scrambled transition.
transition_delay_stop: This parameter shall be used in place of the delay stop parameter for the last CP preceeding a
scrambled to clear transition.
7.1.3 Channel specific messages
7.1.3.1 Channel_setup message
Parameter Number of
instances in message
ECM_channel_ID 1
Super_CAS_ID 1
The Channel_setup message (message_type = 0x0001) is sent by the SCS to set-up a channel once the TCP connection
has been established, as described in subclause 5.1.3.1. It shall contain the Super_CAS_ID parameter, to indicate to the
23. 23 TS 101 197-1 V1.1.1 (1997-06)
ECMG to which CA system and subsystem the channel is intended (indeed, there could be several Super_CAS_IDs
handled by a single ECMG host).
7.1.3.2 Channel_test message
Parameter Number of
instances in message
ECM_channel_ID 1
The Channel_test message (message_type = 0x0002) can be sent at any moment by either side to check:
- the channel is in an error free situation;
- the TCP connection is still alive.
The peer shall reply with a Channel_status message if the channel is free of errors, or a Channel_error message if errors
occurred.
7.1.3.3 Channel_status message
Parameter Number of
instances in message
ECM_channel_ID 1
section_TSpkt_flag 1
AC_delay_start 0/1
AC_delay_stop 0/1
delay_start 1
delay_stop 1
transition_delay_start 0/1
transition_delay_stop 0/1
ECM_rep_period 1
max_streams 1
min_CP_duration 1
lead_CW 1
CW_per_msg 1
max_comp_time 1
The Channel_status message (message_type = 0x0003) is a reply to the Channel_setup message or the Channel_test
message (see subclauses 5.1.3.1 and 5.1.3.5). All the parameters listed above are mandatory.
When the message is a response to a set-up, the values of the parameters are those requested by the ECMG. All these
parameter values will be valid during the whole life time of the channel, for all the streams running on it.
When the message is a response to a test, the values of the parameters shall be those currently valid in the channel.
7.1.3.4 Channel_close message
Parameter Number of
instances in message
ECM_channel_ID 1
The Channel_close message (message_type = 0x0004) is sent by the SCS to indicate the channel is to be closed.
24. 24 TS 101 197-1 V1.1.1 (1997-06)
7.1.3.5 Channel_error message
Parameter Number of
instances in message
ECM_channel_ID 1
error_status 1 to n
error_information 0 to n
A Channel_error message (message type = 0x0005) is the sent by the ECMG when a channel level error occurs. A table
of possible error conditions can be found in subclause 7.1.5.
7.1.4 Stream specific messages
7.1.4.1 Stream_set-up message
Parameter Number of
instances in message
ECM_channel_ID 1
ECM_stream_ID 1
nominal_CP_duration 1
The Stream_setup message (message type = 0x0101) is sent by the SCS to set-up a stream once the channel has been
established, as described in subclause 5.1.3.2.
7.1.4.2 Stream_test message
Parameter Number of
instances in message
ECM_channel_ID 1
ECM_stream_ID 1
The Stream_test message (message_type = 0x0102) is used to request a Stream_status message for the given
ECM_channel_ID and ECM_stream_ID. The Stream_test message can be sent at any moment by either entity. The peer
shall reply with a Stream_status message if the stream is free of errors, or a Stream_error message if errors occurred.
7.1.4.3 Stream_status message
Parameter Number of
instances in message
ECM_channel_ID 1
ECM_stream_ID 1
access_criteria_transfer_mode 1
The Stream_status message (message_type = 0x0103) is a reply to the Stream_setup message or the Stream_test
message.
When the message is a response to a set-up, the values of the parameters are those requested by the ECMG.
When the message is a response to a test, the values of the parameters shall be those currently valid in the stream.
25. 25 TS 101 197-1 V1.1.1 (1997-06)
7.1.4.4 Stream_close_request message
Parameter Number of
instances in message
ECM_channel_ID 1
ECM_stream_ID 1
The ECM_stream_ID is sent by the SCS in the Stream_close_request message (message type = 0x0104) to indicate
which of the streams in a channel is due for closure.
7.1.4.5 Stream_close_response message
Parameter Number of
instances in message
ECM_channel_ID 1
ECM_stream_ID 1
The ECM_stream_ID is sent by the ECMG in the Stream_close_response message (message type = 0x0105) to indicate
which of the streams in a channel is closing.
7.1.4.6 Stream_error message
Parameter Number of
instances in message
ECM_channel_ID 1
ECM_stream_ID 1
error_status 1 to n
error_information 0 to n
A Stream_error message (message type = 0x0106) is the sent by the ECMG when a stream level error occurs. A table of
possible error conditions can be found in subclause 7.1.5.
7.1.4.7 CW_provision message
Parameter Number of
instances in message
ECM_channel_ID 1
ECM_stream_ID 1
CP_number 1
CP_CW_combination CW_per_msg.
CP_duration 0 to 1
access_criteria 0 to 1
The CW_provision message (message_type 0x201) is sent by the SCS to the ECMG and serves as a request to compute
an ECM. The value of the CP_number parameter is the CP number of the requested ECM. The CWs are carried by this
message with their associated CP numbers in the CP_CW_combination parameter, according to the value of lead_CW
and CW_per_msg, as defined during the channel set-up. For instance, if lead_CW = 1 and CW_per_msg = 2, the
CW_provision message for CP N shall contain CWs for CPs N and N + 1.
The SCS is not allowed to send a CW_provision message before having received the ECM_response message for the
previous CPs, except if there has been a time-out expiration, or an error message (in which case the way this error is
handled is left to the discretion of the SCS manufacturer).
26. 26 TS 101 197-1 V1.1.1 (1997-06)
The specific CWs that are passed in the CP_CW_combination to the ECMG via the CW_provision message are derived
from the values of lead_CW and CW_per_msg. The following table shows a number of different values these
parameters can take to achieve different ECMG requirements.
Example Requirements lead_CW CW_per_msg
1 One (1) CW per ECM per CP 0 1
2 The CWs for the current and next CP per ECM 1 1
and the ECMG buffers the current CW from the
previous CW Provision message
3 The CWs for the current and next CP per ECM 1 2
and the ECMG receives both CWs from the SCS
in each CW Provision message
4 Three (3) CWs per ECM per CP 1 3
The graphs in figure 2 depict which CWs shall be passed for a specific CP, based on the different methods listed above.
For any given CP, X-axis, the corresponding CW is portrayed on the Y-axis. In the CW_provision message, the boxed
CWs are the set of CP_CW_combination that shall be passed.
28. 28 TS 101 197-1 V1.1.1 (1997-06)
7.1.4.8 ECM_response message
Parameter Number of
instances in message
ECM_channel_ID 1
ECM_stream_ID 1
CP_number 1
ECM_datagram 1
The ECM_response message (message_type 0x202) is a reply to the CW_provision message. It carries the ECM
datagram, computed by the ECMG, from the information provided by the CW_provision message (and possibly from
other CA specific information). The value of the CP_number parameter shall be the same in the replied ECM_response
message as in the previous incoming CW_provision message (on that stream).
The time-out for the ECM_response message shall be computed by the SCS from the max_comp_time value defined
during channel set-up, and the typical network delays.
7.1.5 Error status
NOTE: TCP connection level errors are beyond the scope of the present document. Only channel, stream and
application level errors are dealt with. These errors occur during the life time of a TCP connection.
There are two different error messages on these interfaces. The Channel_error message for channel wide errors and the
Stream_error message for stream specific errors. These messages are sent by the ECMG to the SCS. When the ECMG
reports an error to the SCS, it is up to the SCS to decide the most appropriate step to be taken. However "unrecoverable
error" explicitly means that the channel or stream (depending on the message used) has to be closed. Most of the error
status listed in the table below can not occur in normal operation. They are mainly provided to facilitate the integration
and debugging phase.
29. 29 TS 101 197-1 V1.1.1 (1997-06)
error_status value Error type
0x0000 DVB Reserved
0x0001 Invalid message
0x0002 Unsupported protocol version
0x0003 Unknown message_type value
0x0004 Message too long
0x0005 Unknown Super_CAS_ID value
0x0006 Unknown ECM_channel_ID value
0x0007 Unknown ECM_stream_ID value
0x0008 Too many channels on this ECMG
0x0009 Too many ECM streams on this channel
0x000A Too many ECM streams on this ECMG
0x000B Not enough CWs to compute ECM
0x000C ECMG out of storage capacity
0x000D ECMG out of computational resources
0x000E Unknown parameter_type value
0x000D Inconsistent length for DVB parameter
0x000F Missing mandatory DVB parameter
0x0010 Invalid value for DVB parameter
0x0011 to 0x6FFF DVB Reserved
0x7000 Unknown error
0x7001 Unrecoverable error
0x7002 to 0x7FFF DVB Reserved
0x8000 to 0xFFFF ECMG specific/CA system specific/User defined
30. 30 TS 101 197-1 V1.1.1 (1997-06)
7.2 EMMG <> MUX and PDG <>MUX
7.2.1 Parameter type values
Parameter_type value Parameter type Type / Units Length (bytes)
0x0000 DVB Reserved - -
0x0001 client_ID uimsbf 4
0x0002 section_TSpkt_flag Boolean 1
0x0003 data_channel_ID uimsbf 2
0x0004 data_stream_ID uimsbf 2
0x0005 datagram user defined variable
0x0006 Bandwidth uimsbf / kbit/s 2
0x0007 Data_type uimsbf 1
0x0008 to 0x6FFF DVB Reserved - -
0x7000 Error_status see subclause 7.2.5 2
0x7001 Error_information user defined variable
0x7002 to 0x7FFF DVB reserved - -
0x8000 to 0xFFFF User defined - -
7.2.2 Parameter semantics
bandwidth: This parameter is used in Stream_BW_request and Stream_BW_allocation messages to indicate the
requested bit rate or the allocated bit rate respectively. It is the responsibility of the EMMG/PDG to maintain the bit rate
generated within the limits specified by the MUX when the bandwidth allocation method is used (optional). It should be
noted that the EMMG/PDG will operate from 0 kbit/s to the negotiated bit rate. The EMMG/PDG will not exceed the
negotiated bit rate. If the bandwidth allocation method is not used the responsibility of bit rate control is not defined in
the present document.
Client_ID: The Client_ID is a 32-bit identifier. It shall identify uniquely an EMMG/PDG across all the EMMGs/PDGs
connected to a given MUX. To facilitate uniqueness of this value, the following rules apply:
- in the case of EMMs or other CA related data, the 2 first bytes of the client_id should be equal to the 2 bytes of
the corresponding CA_system_ID;
- in other cases a value allocated by DVB for this purpose should be used.
Data_stream_ID: This identifier uniquely identifies a EMM/Private Data stream within a channel.
Data_channel_ID: This identifier uniquely identifies a EMM/Private Data channel within a client_ID.
datagram: This is the EMM/Private data. The datagram can be transferred in either section or TS packet format
according to the value of section_TSpkt_flag.
Data_type: Type of data carried in the datagram in the stream. The field shall have the value 0x00 for EMM data.
Values for other private data types are user defined.
Error_status: See subclause 7.2.5.
Error_information: This optional parameter contains user defined data completing the information provided by
error_status. It can be an ASCII text or the parameter ID value of a faulty parameter for example.
section_TSpkt_flag: A value of "0" shall indicate that the EMM or private datagrams carried on the interface are in
MPEG-2 section format. A value of "1" shall indicate that these datagrams are in MPEG-2 transport stream packet
format.
31. 31 TS 101 197-1 V1.1.1 (1997-06)
7.2.3 Channel specific messages
7.2.3.1 Channel_setup message
Parameter Number of
instances in message
client_ID 1
data_channel_ID 1
section_TSpkt_flag 1
The Channel_setup message (message_type = 0x0011) is sent by the EMMG/PDG to the MUX to set-up a channel once
the TCP connection has been established, as described in subclause 5.2.3.1. It shall contain the client_ID parameter
indicating to the MUX the EMMG/PDG that is opening the channel.
7.2.3.2 Channel_test message
Parameter Number of
instances in message
client_ID 1
data_channel_ID 1
The Channel_test message (message_type = 0x0012) can be sent at any moment by either side to check:
- the channel is in an error free situation;
- the TCP connection is alive.
The peer shall reply with a Channel_status message if the channel is free of errors, or a Channel_error message if errors
occurred.
7.2.3.3 Channel_status message
Parameter Number of
instances in message
client_ID 1
data_channel_ID 1
section_TSpkt_flag 1
The Channel_status message (message_type = 0x0013) is a reply to the Channel_setup message or the Channel_test
message (see subclauses 5.2.3.1 and 5.2.3.6). All the parameters listed above are mandatory.
The values of the parameters shall be those currently valid in the channel.
7.2.3.4 Channel_close message
Parameter Number of
instances in message
client_ID 1
data_channel_ID 1
The channel close message (message_type = 0x0014) is sent by the EMMG/PDG to indicate the channel is to be closed.
32. 32 TS 101 197-1 V1.1.1 (1997-06)
7.2.3.5 Channel_error message
Parameter Number of
instances in message
client_ID 1
data_channel_ID 1
error_status 1 to n
error_information 0 to n
A Channel_error message (message type = 0x0015) is the sent by the MUX when a channel level error occurs. A table
of possible error conditions can be found in subclause 7.2.5.
7.2.4 Stream specific messages
7.2.4.1 Stream_setup message
Parameter Number of
instances in message
client_ID 1
data_channel_ID 1
data_stream_ID 1
data_type 1
The Stream_setup message (message_type = 0x0111) is sent by the EMMG/PDG to set-up a stream once the channel
has been established, as described in subclause 5.2.3.2.
7.2.4.2 Stream_test message
Parameter Number of
instances in message
client_ID 1
data_channel_ID 1
data_stream_ID 1
The Stream_test message (message_type = 0x0112) is used to request a Stream_status message for the given client_ID,
data_channel_ID and data_stream_ID. The Stream_test message can be sent at any moment by either entity. The peer
shall reply with a Stream_status message if the stream is free of errors, or a Stream_error message if errors occurred.
7.2.4.3 Stream_status message
Parameter Number of
instances in message
client_ID 1
data_channel_ID 1
data_stream_ID 1
data_type 1
The Stream_status message (message_type = 0x0113) is a reply to the Stream_setup message or the Stream_test
message.
The values of the parameters shall be those currently valid in the stream.